-
Notifications
You must be signed in to change notification settings - Fork 329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Node.js v16 in all Actions #909
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
henrymercer
force-pushed
the
henrymercer/bump-node-js-to-v16
branch
from
February 3, 2022 19:07
1a8a10b
to
1ed6569
Compare
edoardopirovano
approved these changes
Feb 7, 2022
I'll hold off merging this until the next release is out, so this can sit in |
v1.0.32 was just released. Should we merge this one now? |
henrymercer
force-pushed
the
henrymercer/bump-node-js-to-v16
branch
from
February 8, 2022 10:28
1ed6569
to
3db84ce
Compare
Rebased on |
Some CI jobs are failing due to the |
henrymercer
force-pushed
the
henrymercer/bump-node-js-to-v16
branch
from
February 8, 2022 12:08
3db84ce
to
007f040
Compare
henrymercer
changed the base branch from
main
to
henrymercer/fix-windows-latest-ci-jobs
February 8, 2022 12:09
henrymercer
force-pushed
the
henrymercer/bump-node-js-to-v16
branch
2 times, most recently
from
February 8, 2022 12:53
f35e5d7
to
6f89a18
Compare
henrymercer
force-pushed
the
henrymercer/fix-windows-latest-ci-jobs
branch
from
February 8, 2022 13:31
e43cec9
to
2ebc770
Compare
henrymercer
force-pushed
the
henrymercer/bump-node-js-to-v16
branch
from
February 8, 2022 13:33
6f89a18
to
a8e4927
Compare
henrymercer
force-pushed
the
henrymercer/fix-windows-latest-ci-jobs
branch
from
February 8, 2022 13:50
2ebc770
to
8dd2b9a
Compare
This is now in active LTS status.
The upgrade to Node.js v16 warrants a minor version bump.
henrymercer
force-pushed
the
henrymercer/bump-node-js-to-v16
branch
2 times, most recently
from
February 8, 2022 16:19
f7b9ff3
to
76b7276
Compare
henrymercer
force-pushed
the
henrymercer/bump-node-js-to-v16
branch
from
February 8, 2022 16:19
76b7276
to
8f27994
Compare
Base automatically changed from
henrymercer/fix-windows-latest-ci-jobs
to
main
February 8, 2022 17:05
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Node.js v16 is in active LTS status and is now the default for Actions, so this PR upgrades to it. This warrants a minor version bump, so we bump the version to v1.1.0. As a bonus we remove some stub type definitions.
Merge / deployment checklist